Implement ComputeTriangleAreas, GetNonManifoldEdges and RemoveNonManifoldEdges in t::geometry::TriangleMesh #6657
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes. |
nsaiapova
force-pushed
the
wip/remove-non-manifold-edges
branch
from
188c467
to
3b8f865
Compare
benjaminum
requested changes
Feb 26, 2024
ssheorey
reviewed
Mar 5, 2024
There was a problem hiding this comment.
Thanks @nsaiapova! Some minor comments. Feel free to ignore comments labeled with nit. We can chat about the algorithm....
| @@ -1212,5 +1212,84 @@ TEST_P(TriangleMeshPermuteDevices, SelectByIndex) { | |||
| box_untouched.GetTriangleIndices())); | |||
| } | |||
|
|
|||
| TEST_P(TriangleMeshPermuteDevices, RemoveNonManifoldEdges) { | |||
There was a problem hiding this comment.
Thanks for adding this - looks like we didn't have a test for this in legacy geometry.
nsaiapova
force-pushed
the
wip/remove-non-manifold-edges
branch
from
3b8f865
to
20782b4
Compare
benjaminum
reviewed
Apr 16, 2024
|
Hi @nsaiapova can you take a look at the failing CI checks? |
nsaiapova
force-pushed
the
wip/remove-non-manifold-edges
branch
from
20782b4
to
aa7a3ce
Compare
Split the logic from ComputeSurfaceArea into a helper static function and introduce a new method which computes triangle areas and writes the resulting tensor into attributes of the mesh.
nsaiapova
force-pushed
the
wip/remove-non-manifold-edges
branch
from
aa7a3ce
to
110aebd
Compare
... and t::geometry::TriangleMesh::GetNonManifoldEdges methods. The methods are defined in geometry::TriangleMesh API. t::geometry::TriangleMesh::GetNonManifoldEdges mimics the logic of the legacy method. t::geometry::TriangleMesh::RemoveNonManifoldEdges follows the logic of the legacy method but there are a few differences: * the main difference is that the outer while-loop is removed. I don't see how after the first iteration any edge can have more than 2 adjacent triangles, which makes the further iterations unnecessary. * I count triangles with non-negative areas immediately and do not rely on the total number of adjacent triangles (which would also include triangles marked for removal). * To choose a triangle with the minimal area out of the existing adjacent triangles I use a heap structure.
nsaiapova
force-pushed
the
wip/remove-non-manifold-edges
branch
from
110aebd
to
e25faf0
Compare
|
Update unit tests to unordered comparison, since order of output is platform dependent. |
ssheorey
approved these changes
Jun 14, 2024
…pty areas property if there are no triangles.
ssheorey
force-pushed
the
wip/remove-non-manifold-edges
branch
from
6f2dd07
to
b008cb7
Compare
…reas property if there are no triangles.
ssheorey
force-pushed
the
wip/remove-non-manifold-edges
branch
from
74230d4
to
cf99e70
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement a few methods which are available with the geometry::TriangleMesh API.
Type
Motivation and Context
Checklist:
python util/check_style.py --applyto apply Open3D code styleto my code.
updated accordingly.
results (e.g. screenshots or numbers) here.
Description
In this PR three methods for t::geometry::TriangleMesh are implemented.
t::geometry::TriangleMesh::ComputeTriangleAreas
Split the logic from ComputeSurfaceArea into a helper static function
and introduce a new method which computes triangle areas and writes the
resulting tensor into attributes of the mesh.
IIUC, in geometry::TriangleMesh the corresponding function is GetSurfaceArea(std::vector &areas), where the areas are filled with the triangle areas.
t::geometry::TriangleMesh::GetNonManifoldEdges mimics the logic of the legacy method.
t::geometry::TriangleMesh::RemoveNonManifoldEdges follows the logic of
the legacy method but there are a few differences:
see how after the first iteration any edge can have more than 2
adjucent triangles, which makes the further iterations unnecessary.
on the total number of adjacent triangles (which would also include
triangles marked for removal).
adjacent triangles I use a heap structure.